Skip to main content

This is a new service – your feedback will help us to improve it.

Uttlesford District Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

4 Individual 1 Area

reference
1/76/25-192
name
4 Individual 1 Area
tree-preservation-order

undefined

1/76/25-192
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((0.202966 51.906645,0.203089 51.906746,0.203127 51.906780,0.203165 51.906822,0.203187 51.906849,0.203214 51.906889,0.203248 51.906952,0.202427 51.907093,0.202335 51.907111,0.202311 51.907071,0.202276 51.907005,0.202190 51.906853,0.202204 51.906850,0.202147 51.906756,0.202173 51.906750,0.202121 51.906659,0.202091 51.906666,0.202068 51.906626,0.201989 51.906644,0.201958 51.906631,0.201936 51.906635,0.201916 51.906656,0.202015 51.906823,0.202020 51.906856,0.201814 51.906900,0.201733 51.906584,0.201734 51.906526,0.201778 51.906441,0.201777 51.906363,0.201768 51.906273,0.201761 51.906087,0.201735 51.905878,0.201739 51.905786,0.201732 51.905683,0.201754 51.905678,0.201790 51.905679,0.201803 51.905696,0.201819 51.905725,0.201809 51.905787,0.201809 51.905807,0.201811 51.905822,0.201817 51.905835,0.201862 51.905916,0.201897 51.905972,0.202128 51.906306,0.202565 51.906201,0.202613 51.906219,0.202625 51.906226,0.202652 51.906253,0.202652 51.906255,0.202658 51.906263,0.202671 51.906277,0.202823 51.906477,0.202872 51.906473,0.202914 51.906476,0.202947 51.906483,0.202968 51.906512,0.202920 51.906583,0.202966 51.906645)))
point
POINT (0.202375 51.906588)
notes
entry-date
1976-10-26
start-date
1976-10-26
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Uttlesford District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL